NetNews Offline 2/NetNews Offline Volume 2.iso/news/comp/lang/c-part2/12056

Internet Message Format | 1996-08-05 | 1.6 KB

Path: nntp.snfc21.pbi.net!usenet
From: [e-mail]
Newsgroups: comp.unix.programmer,comp.lang.c
Subject: Re: Q: Size of a program
Date: 28 Mar 1996 23:34:33 GMT
Organization: Pacific Bell Internet Services
Message-ID: <4jf7m9$[e-mail]>
References: <[e-mail]>
Reply-To: [e-mail]
NNTP-Posting-Host: ppp-5-34.rdcy01.pbinet.com
X-Newsreader: IBM NewsReader/2 v1.03

In <[e-mail]>, Artur Wojdat <[e-mail]> writes:
>Hello everybody,
>    I have bunch of programs designed to query Sybase and print the
>results. Nothing special about that but the source code for most of them
>takes up about 2K of disk space and compiled version ... over 600K !!!
>    We have some limitations on our system and I am not able to have
>all my programs compiled. So, is there a way to make the executables
>shrink in size ?? Any suggestions will be greatly appreciated

Sure. Make as many of them as possible shared objects, or alternately, create a 'master'
interface program and menu out the sub programs as choices to the user, exec()
or spawn() out new processes to the sub-progs. What I would do Is a combo of
the two methods, createing one or two or three shared libraries and putting all the
'lower level' subroutines (user input, data display, housekeeping, db queries,
various and sundry routines) in the libs and dividing up the higher level stuff
among my executable objects.
Frankly, I can't think of why anyone wouldn't do it that way. Maybe I'm
a traditionalist.
-----------------------------
Reality Meter: [\.....], thought so
-----------------------------